Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%



Title: Multiple Deal Pipeline


To cater companies that have multiple sales process for different products or markets.

Available from Estate Plan.

Pipeline:

 Stage:

Associations:

Deal created via API:


Migrations:



Fixtures:

            

CRM Data Migration:

  ImportDealCsv -

      Deal is going to map with pipeline and corresponding stage according to below conditions:

Other Migrations -

     Deal is going to map with pipeline and corresponding stage according to below conditions


Filters:

Deal stage always comes with Pipeline context.

   SalesAccount & Contact - DealPipeline and Deal Stage are available in the filter options but not sticky.


   Deal:



Frontend


Deal pipeline frontend workflow.png

Deal multiple pipeline UML Diagrams  (Model)


Deal pipeline Settings:

Screen Shot 2017-04-28 at 6.30.36 PM.png


Route: deal-pipeline

Controllers: deal-pipeline

Components:  deal-pipeline



Deal Field Settings:


Deal pipelines, Deal stages  Fields :-   Choices should be hidden, and link should be provided to Deal pipeline settings.

Territories Field :- Choices should be hidden, and link should be provided to Territories settings page.

Owners Field :-  Choices should be hidden, and link should be provided to  User settings page.



Deal Filters:

Deal filters , pipeline field should be added , which is single selection Dropdown.

Deal pipeline filed will be default sticky for deal filter view and always pipeline will be part of the rule associated with any view(Default, Custom Shared, Custom)

Deal stages field in filter will be updated based on change with deal pipeline field.


Account Filters :

Account filters has both pipeline and stage as non sticky field in filters.

Choosing Deal pipeline field and choosing a value in that field will update the deal stage field choices and make it visible.

Choosing Deal stage field will prefill Deal pipeline field with user prefered pipeline and will update deal stage field choices.


Deal Funnel :

Deal funnel page should have pipeline dropdown , which filter the deals based on views.

Pipeline dropdown shows all pipeline only in Default View.

Custom View and Custom Shared view will have the pipeline associated with that rule.


User Pipeline :

Pipeline preference is categorised into account level and user level

User level pipeline can be set in profile settings, when the user preferred pipeline is deleted the user preference is shifted to account level pipeline


RSpecs

RSpec coverage after this change across deal module is >95%.

Links

Git Initial Squash Commit : https://github.com/freshdesk/freshsales/commit/c01ca031ef247795da8601dd3756d7540e7e7a38

Spec : 



Frontend Test case Coverage to Components related to Deal pipeline module .

components/deal-pipeline/                                      93.86%
templates/shared/deal-pipeline/                              91.69%
components/modals/bulk-update/                           97.81%
components/filters/dependent-dropdown/               100%
components/modals/edit-custom-field/                    67.01%
components/modals/deal-form/                               60.38%